There are two types of logs output: one is the log for SuperMap iDesktopX, and the other is for SuperMap iObjects, recording information from the desktop and component operations respectively. Log contents include output info from the program's output window, exception details, etc. Logs are stored in the "log" folder under the "bin" directory in the root path.

　　#!/bin/bash 　　export ORACLE_HOME=/opt/oracleClient (path to the client) 　　export PATH=$PATH:$ORACLE_HOME 　　export LD_LIBRARY_PATH=$ORACLE_HOME:$LD_LIBRARY_PATH

After setting the Oracle client environment variable, restart SuperMap iDesktopX in the same Terminal to use Oracle data sources normally. To create or connect to an Oracle data source, configure the Oracle client in the environment running the desktop, add the client to LD_LIBRARY_PATH. A profile example can be provided, and configure tnsnames.ora. If connecting via EZConnect, tnsnames configuration is unnecessary.

The source code in the develop branch depends on an unreleased, in-development version of iObjects Java. Users cannot obtain the newest version of iObjects, leading to compilation errors. It is recommended to fetch the source code from fixed versions in the Tags and download the corresponding iObjects Java version from the SuperMap official website for compilation.

There are three reasons for this: First, no license is configured; second, the license configuration is unsuccessful; third, the license has expired. For the first two reasons, the solution is to reconfigure the license. Configuration methods differ for Windows and Linux operating systems. Refer to the license configuration sections in Windows Configuration Guide and Linux Configuration Guide for specific steps.

On SUSE, third-party database clients must be installed to load SDX data engines correctly. Failure to load one SDX engine affects others, preventing any data sources from opening or the program from starting. SDX data engine files requiring third-party database clients include: libSuEngineSRDB.sdx, libSuEngineOracle.sdx, libSuEngineDMCI.sdx, libSuEngineOsp.sdx, libSuEngineAltibase.sdx, libSuEngineDB2.sdx, libSuEngineKDB.sdx. For example: If using an Oracle data source, first install the Oracle client, then delete all *.sdx listed above except libSuEngineOracle.sdx, and restart SuperMap iDesktopX. Similarly, handle other database engines as needed.

The solution is: Keep libSuEngineImagePlugin.sdx and the required database engine files in the bin directory of the product package, and delete unnecessary database engine files (the *.sdx in the list above).

The code on Git has two branches: master and develop. The master branch is the main stable version branch, updated with each stable release. The develop branch is the development branch, updated daily with code modifications but not guaranteed for stability. Therefore, the develop version may throw exceptions.

This is caused by missing Chinese fonts in the Linux system. Place a Chinese font in the jre/jre/lib/fonts folder under the product package directory, and the program interface text will display normally.

During map visualization, special fonts like "microsoft yahei" are used, which may not exist in Linux operating systems, causing abnormal display of map annotations and text features. Refer to the attachments fonts_1.zip and fonts_2.zip, which contain mainstream common fonts. When using this program or source code on Linux, download and extract them to the "root directory/support/fonts/" directory (create it if it doesn't exist), and add the environment variable SUPERMAP_ROOT with its value set to "root directory/support/". Then, configure the environment according to 《SuperMap iDesktopX 8C Extension Development Guide.doc》 to display text features normally.

If Linux lacks a Chinese environment, change the published map name to English; or publish the map service with a Chinese name on a Linux system with a Chinese environment.

Copy the "libstdc++.so.6" file from the support folder in the desktop package to the Bin directory of the component to resolve this issue.

The desktop startup requires a graphical interface library and can only be launched and operated graphically. First, ensure the remote server has a graphical interface library configured. Second, choose a visual remote connection tool. SecureCRT is a command-line tool; switch to another remote control tool like VNC or Xmanager, both of which allow graphical operations on UNIX or Linux but require configuration. For VNC configuration, refer to How to Configure VNC on CentOS 5.5 and VNC Installation and Configuration.

Notes: If encountering this issue on other Linux operating systems, apply the same solution.

Executing functions like modifying colors or saving layouts to the template library writes data to the installation path. When starting iDesktopX by double-clicking SuperMap iDesktopX.exe, there is no permission to write to system directories, causing the execution to fail. Run SuperMap iDesktopX.exe as an administrator to resolve this.

When starting iDesktopX by double-clicking SuperMap iDesktopX.exe, there is no permission to read/write data in system directories. Resolve this by:

• Moving data to non-system directories and changing output paths to non-system directories; (Recommended)
• Right-clicking SuperMap iDesktopX.exe and selecting "Run as administrator";
• Right-clicking SuperMap iDesktopX.exe, selecting "Properties", changing EXE permissions to administrator, and rerunning the EXE;

This is due to a missing Microsoft Visual C++ runtime. In the support folder under the product installation path \SuperMap\SuperMap iDesktopX, double-click vcredist110_x64.exe. After successfully installing Microsoft Visual C++ 2012, it will start normally.

This is caused by a DLL file failing to load. Resolve it by:

1. Restarting SuperMap iDesktopX;
2. If the error persists, open the SuperMap.Desktop.Parameter.xml file in the product package\configuration folder. Change " <loadDll loadDll="true"/>" to false;
3. After modification, restart SuperMap iDesktopX.

SuperMap iDesktopX startup requires JRE 1.7 or later. If the JRE version is insufficient, Java fails to start. Solutions include:

• Uninstall the locally installed older JRE, install JRE 1.7 or newer, then restart Java;
• The Java product package includes a JRE 1.7 environment. During startup, it prioritizes the local configuration, causing failure. If users don't want to uninstall the local JRE, modify the startup.sh script. Change "export PATH=$SUPERMAP_ROOT:$LD_LIBRARY_PATH:$JRE_PATH:$PATH" to "export PATH=$JRE_PATH:$SUPERMAP_ROOT:$LD_LIBRARY_PATH:$PATH". Re-execute startup.sh to start Java.

Notes: This issue is resolved in version 9D; JRE environment incompatibility no longer prevents startup.